-
Notifications
You must be signed in to change notification settings - Fork 124
Implement basic categorization for libraries in dartdoc #1641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0129842
to
7423e0e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add some usage instructions to the README?
generates docs. | ||
|
||
```yaml | ||
dartdoc: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why have a dartdoc
top key in dartdoc_options.yaml
?
Couldn't categoryOrder
just be at the top?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was paralleling with analysis_options.yaml
, which has analyzer and linter subsections. There might be an opportunity for sections for other tools using dartdoc libraries, such as the still vaporware API comparison gadget.
README.md
Outdated
@@ -114,6 +142,9 @@ and then you can insert it via `{@macro template_name}`, like | |||
/// More comments | |||
``` | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
extra whitespace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Document my new feature? In our moment of triumph?
README.md
Outdated
@@ -114,6 +142,9 @@ and then you can insert it via `{@macro template_name}`, like | |||
/// More comments | |||
``` | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
generates docs. | ||
|
||
```yaml | ||
dartdoc: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was paralleling with analysis_options.yaml
, which has analyzer and linter subsections. There might be an opportunity for sections for other tools using dartdoc libraries, such as the still vaporware API comparison gadget.
ack
…On Fri, Mar 23, 2018 at 11:42 AM jcollins-g ***@***.***> wrote:
***@***.**** commented on this pull request.
Document my new feature? In our moment of triumph?
------------------------------
In README.md
<#1641 (comment)>:
> @@ -114,6 +142,9 @@ and then you can insert it via ***@***.*** template_name}`, like
/// More comments
```
+
done.
------------------------------
In README.md
<#1641 (comment)>:
> @@ -95,6 +95,34 @@ authoring doc comments for Dart with `dartdoc`.
## Advanced features
+### dartdoc_options.yaml
+
+Creating a file named dartdoc_options.yaml at the top of your package can change how Dartdoc
+generates docs.
+
+```yaml
+dartdoc:
This was paralleling with analysis_options.yaml, which has analyzer and
linter subsections. There might be an opportunity for sections for other
tools using dartdoc libraries, such as the still vaporware API comparison
gadget.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#1641 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABCir1ZQEaYcyu1b_DA6p4fQk3zr3_6ks5thUIGgaJpZM4S3vNP>
.
|
Fixes #1610.
Also, this is the beginning of a longer chain to implement #1353.
This allows you to mark libraries with
{@category Foo}
and have libraries appear in a category in the sidebar and in the main package view. Uncategorized libraries appear at the top. An example:https://user-images.githubusercontent.com/14116827/37685847-3f34c478-2c52-11e8-82b9-6b1485a5a05d.png
This PR also eliminates the "use-categories" flag. The "old style" meaning of categories meaning packages is now gone. The flag is now ignored and Dartdoc decides whether to organize libraries into packages based on whether there are multiple packages in the requested set of libraries.